-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update docs and readme #62
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super neat docs!
apps/api/README.md
Outdated
- (optional) `PORT` on which API is made available. By default is port 3000 | ||
- (optional) `ENVIRONMENT` which environment we are using ( 'mainnet' | 'testnet' | 'local'). By default is 'mainnet' | ||
- `BRIDGE_HUB_ADDRESS` | ||
- `SHARED_BRIDGE_ADDRESS` | ||
- `STATE_MANAGER_ADDRESSES` CSV list of State managers addresses | ||
- `L1_RPC_URLS` as CSV list of RPC URLs. For example, `https://eth.llamarpc.com,https://rpc.flashbots.net/fast`. You can check [Chainlist](https://chainlist.org/) for a list of public RPCs | ||
- (optional) `PRICING_SOURCE` which pricing source to use ('dummy' | 'coingecko'). By default is dummy | ||
- (optional) `DUMMY_PRICE` for dummy pricing source. Default is undefined | ||
- (required if 'coingecko' is selected)`COINGECKO_API_KEY`, `COINGECKO_BASE_URL` and `COINGECKO_API_KEY` depending on your API plan. You can get an API Key creating an account on [Coingecko's site](https://www.coingecko.com/en/api) | ||
- `METADATA_SOURCE` which metadata source to use ('github' | 'local' | 'static') | ||
- (required if METADATA_SOURCE is 'github') `METADATA_TOKEN_URL` Metadata tokens URL | ||
- (required if METADATA_SOURCE is 'github') `METADATA_CHAIN_URL` Metadata chains URL | ||
- (required if METADATA_SOURCE is 'local') `METADATA_TOKEN_JSON_PATH` Metadata tokens JSON file path (see examples on `packages/metadata`) | ||
- (required if METADATA_SOURCE is 'local') `METADATA_CHAIN_JSON_PATH` Metadata chain JSON file path (see examples on `packages/metadata`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is going the extra extra mile but, what do you think about using a Markdown table for this part? You can use this tool to generate your tables in an easier way
Eg
Name | Description | Default | Notes |
---|---|---|---|
PORT | Port on which API is made available. | "3000" | |
ENVIRONMENT | Environment used ('mainnet' | 'testnet' | 'local') | "mainnet" | |
BRIDGE_HUB_ADDRESS | |||
... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks 🫶
packages/pricing/README.md
Outdated
|
||
1. To create a new provider, create it inside [`providers`](./src/providers/) folder and implement the [`IPricingProvider`](./src/interfaces/pricing.interface.ts) interface. | ||
|
||
> Note 1: is provider implementation responsibility to map token addresses to their internal id if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It took me some seconds to understand this phrase at first, wdyt about these small changes?
> Note 1: is provider implementation responsibility to map token addresses to their internal id if needed. | |
> Note 1: it is the provider's responsibility to map token addresses to their internal id if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥 🔥 🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
🤖 Linear
Closes ZKS-150
Description
Add docs and README files for packages